home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98a.txt
/
000088_icon-group-sender _Wed Mar 4 09:11:01 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
2KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.7/8.8.7) with SMTP id JAA06715
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Wed, 4 Mar 1998 09:10:58 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA05299; Wed, 4 Mar 1998 09:10:57 -0700
Message-Id: <s4fd27c1.030@housmtp.oceaneering.com>
X-Mailer: Novell GroupWise 4.1
Date: Wed, 04 Mar 1998 10:06:02 -0600
From: Charles Hethcoat <CHETHCOA@oss.oceaneering.com>
To: icon-group@optima.CS.Arizona.EDU
Subject: Icon translation
Mime-Version: 1.0
Content-Type: text/plain
Content-Disposition: inline
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 796
G. Peterson wrote:
>If you intend to maintain the program in C (thus making it essentially a
one-shot creation process) then why don't you just write it in C to begin
with??
Correct. Remember the butter commercials? "It's not nice to fool Mother
Nature."
That's how a lot of this recent thread strikes me. If you need the machine
speed of C, and nothing else matters, then program in C. If you want the
programmer speed of Icon (which is considerable), use Icon.
I use Icon mostly because it saves my brain from a lot of pain. But my
programs are small and used mostly by me, and are designed from the start
to save my time.
The only real way to speed up Icon is to build a custom computer
architecture specifically to execute the Icon-generated abstract code.
Charles Hethcoat